Conversation
The package and npm registry were both at 5.0.4, so publishing would conflict. This bumps the package to 5.0.5 and records the matching release-note entry so publish workflow and metadata checks stay aligned. Constraint: Keep README release notes in sync with package version for metadata guardrails Rejected: Publish 5.0.4 again | npm rejects duplicate published versions Confidence: high Scope-risk: narrow Reversibility: clean Directive: For every future version bump, update README release notes in the same change Tested: npm test Tested: npm pack --dry-run
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Automated by scripts/agent-branch-finish.sh (PR flow).